Node / meshtastic / Meshtastic-Android / commits / 2ff7ecf

Parents : b9724eb

Author : James Rich <2199651+jamesarich@users.noreply.github.com>

Signature : Signature validation error

Date : 2026-06-22T15:23:59-05:00

Committer : GitHub <noreply@github.com>

Date : 2026-06-22T15:23:59-05:00

docs: de-submodule protos, sync constitution to v1.3.3, prune stale governance refs (#5905)

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

Signed-off-by: James Rich <james.a.rich@gmail.com>

12 files changed, 48 insertions(+), 37 deletions(-)

M .claude/settings.json +1 -2

M .github/copilot-instructions.md +1 -2

M .skills/design-standards/SKILL.md +8 -7

M .skills/new-branch/SKILL.md +7 -6

M .skills/speckit/SKILL.md +3 -2

M .specify/memory/constitution.md +15 -10

M .specify/templates/checklist-template.md +3 -2

M .specify/templates/plan-template.md +5 -2

M .specify/templates/spec-template.md +1 -1

M .specify/templates/tasks-template.md +1 -1

M AGENTS.md +2 -1

M CLAUDE.md +1 -1

--- a/.claude/settings.json

+++ b/.claude/settings.json

"$comment": "Team-wide Claude Code config. (1) Read guards: Claude does NOT read .aiexclude/.copilotignore, so the big-file protections live here. 'deny' = never read (Crowdin-managed translations); 'ask' = prompt first (big files rarely needed in full — prefer .skills/compose-ui/strings-index.txt for strings; signing keys should never be read into context). (2) Hooks front-run this repo's own CI gates locally — see .claude/hooks/*.sh for what each does. The pre-bash-guard spotlessApply-on-commit hook is the heaviest (runs gradle at commit time); remove its PreToolUse entry if it's too eager for your workflow.",

"permissions": {

"deny": [

],

"ask": [

"Read(**/composeResources/**/values/strings.xml)",

--- a/.github/copilot-instructions.md

+++ b/.github/copilot-instructions.md

## Build, Test & Lint (essentials)

```bash

[ -f local.properties ] || cp secrets.defaults.properties local.properties

```

```bash

--- a/.skills/design-standards/SKILL.md

+++ b/.skills/design-standards/SKILL.md

Android-specific guidance for applying the Meshtastic design standards. All visual rules, color palettes, accessibility requirements, and cross-platform conventions live upstream.

> **Source of truth:** [`meshtastic/design/standards/`](https://github.com/meshtastic/design/tree/main/standards)

> If this skill diverges from upstream, **upstream wins**.

## 1. How to Use the Standards

Before implementing any UI:

1. **Read the upstream standards** — they include a full agent implementation checklist

3. Apply the Android-specific mappings below

## 2. Android / Compose Mappings

### Theme Tokens

The upstream standards define M3 role mappings (Section 8). In this codebase:

- Use M3 tokens (`MaterialTheme.colorScheme.primary`, `.surface`, etc.) — never raw hex values

### Brand Colors → Compose

| Standard Name | Hex | Compose Usage |

| Error | `#E05252` | `MaterialTheme.colorScheme.error` |

| Link | `#9BA8E0` | Blue 400 — for clickable text |

### Key Rules (Android-specific)

- **Icons:** Use `MeshtasticIcons` (from `core/ui/icon/`), not `material.icons.Icons`

- **Touch targets:** 44×44dp minimum (M3 default is 48dp — compliant)

## 3. App Icons

## 4. Settings Validation Reference

--- a/.skills/new-branch/SKILL.md

+++ b/.skills/new-branch/SKILL.md

```

## Branch Naming

| Prefix | Use for |

| :--- | :--- |

- [ ] `ANDROID_HOME` exported (see AGENTS.md workspace bootstrap).

- [ ] Optional: run `./gradlew assembleDebug` once to catch environment regressions before editing.

If the user's opening prompt is a sweeping audit or investigation (e.g. *"audit changes since

--- a/.skills/speckit/SKILL.md

+++ b/.skills/speckit/SKILL.md

The project constitution at `.specify/memory/constitution.md` defines non-negotiable principles.

All specs, plans, and tasks are validated against it during `/speckit.analyze`.

1. **KMP Core** — Business logic in `commonMain` only

2. **Zero Lint Tolerance** — `spotlessCheck` + `detekt` must pass

3. **Compose Multiplatform UI** — CMP, not Android-only Compose

4. **Privacy First** — No PII/location/key exposure

5. **Design Standards Compliance** — Review against Meshtastic design standards; cross-platform features must reference an upstream spec from `meshtastic/design/features/`

## Extension Hooks

--- a/.specify/memory/constitution.md

+++ b/.specify/memory/constitution.md

<!--

SYNC IMPACT REPORT

==================

Modified principles:

Added sections: None.

Removed sections: None.

Follow-up TODOs: None.

-->

or any debug output.

- Secrets MUST be git-ignored and MUST NOT be committed to the repository under any

circumstances.

<!-- Rationale: Meshtastic users rely on the mesh for private, off-grid communications. Data leaks could endanger users in sensitive deployments. -->

### V. Design Standards Compliance

No alternative DI framework may be introduced.

- **Navigation**: JetBrains Navigation 3 for multiplatform routing with RESTful deep

linking. All navigation MUST use `MeshtasticNavDisplay`.

introduced in KMP modules.

## Operational Standards

Constitution Check confirming all seven principles were evaluated. Complexity violations

require explicit justification in the Complexity Tracking table of the plan document.

--- a/.specify/templates/checklist-template.md

+++ b/.specify/templates/checklist-template.md

- [ ] CHK001 — Principle I (KMP Core): All code in `commonMain`? No `java.*`/`android.*` imports? [Consistency]

- [ ] CHK002 — Principle II (Zero Lint Tolerance): `spotlessApply` + `detekt` pass? [Consistency]

- [ ] CHK003 — Principle III (CMP UI): Compose Multiplatform composables? `NumberFormatter.format()` for floats? Navigation 3 patterns? [Consistency]

- [ ] CHK005 — Principle V (Design Standards): UI reviewed against Meshtastic design standards? Cross-platform features linked to upstream spec in `meshtastic/design/features/`? [Consistency]

## [Category 1]

--- a/.specify/templates/plan-template.md

+++ b/.specify/templates/plan-template.md

Multiplatform patterns, `MeshtasticNavDisplay`/`NavigationBackHandler` where relevant,

and pre-formats floats with `NumberFormatter.format()`.

- **IV. Privacy First**: Confirm the change does not log or expose PII, location data,

- **V. Design Standards Compliance**: For any user-facing UI, record how the design was

checked against the Meshtastic Client Design Standards. For cross-platform features,

link the upstream behavior spec from `meshtastic/design/features/` or justify N/A.

post-push CI check command (`gh pr checks` or `gh run list`) before implementation starts.

If any gate cannot be met, the exception MUST be justified in the Complexity Tracking

--- a/.specify/templates/spec-template.md

+++ b/.specify/templates/spec-template.md

- [ ] No PII, location data, or cryptographic keys logged or exposed

- [ ] No new network calls that transmit user data

## Success Criteria *(mandatory)*

--- a/.specify/templates/tasks-template.md

+++ b/.specify/templates/tasks-template.md

- [ ] TXXX [P] Documentation updates in docs/

- [ ] TXXX Code cleanup and refactoring

- [ ] TXXX [P] Review user-facing UI against Meshtastic design standards and document any approved deviations

- [ ] TXXX [P] Run constitution-required verification (`spotlessCheck`, `detekt`, and relevant compile/test tasks)

- [ ] TXXX [P] Additional unit/integration tests (if requested) in the appropriate test source sets

- [ ] TXXX Validate quickstart/README or developer workflow docs if contributor workflow changed

--- a/AGENTS.md

+++ b/AGENTS.md

<context_and_memory>

- **Project Goal:** Decouple business logic from Android for multi-platform (Android, Desktop, iOS).

- **Agent Memory:** Skim the top (most recent) entry of `.agent_memory/session_context.md` for current state — it is capped at ~5 entries; older handovers live in `session_context.archive.md` (read only if you need historical detail).

- **Skills Directory (CONSULT THESE FIRST):**

- `.skills/project-overview/` - Codebase map, namespacing, **Bootstrap Steps**.

- `.skills/kmp-architecture/` - Expect/actual, source-sets, conventions.

- `.skills/compose-ui/` - Adaptive UI, **String Resources (consult strings-index.txt first)**.

- `.skills/navigation-and-di/` - Navigation 3 & Koin annotations.

- `.skills/testing-ci/` - Validation commands, **CI Architecture**.

- `.skills/ci-cost-control/` - **CI Budgeting & Monitoring**.

--- a/CLAUDE.md

+++ b/CLAUDE.md

- **Think First:** Outline step-by-step reasoning inside `<thinking>` tags before writing code or shell commands.

- **Skills:** Load only the `.skills/` module relevant to the current task — don't read them all. Start with `.skills/project-overview/SKILL.md` (codebase map, bootstrap, troubleshooting).

- **Delegate to keep context lean** (this is a 20+ module KMP repo):

- **Broad searches** ("where is X used", "find all implementers of Y") → dispatch the `Explore` subagent so file dumps stay out of the main context; you get back the conclusion.

- **Gradle builds/tests/lint** → dispatch the `gradle-runner` subagent. A full `assembleDebug`/`allTests` log is thousands of lines; the subagent returns only pass/fail + failing tests. Don't run heavy `./gradlew` tasks inline.